When playing a track in the car it would be really useful if I could mark the
current and/or the last track. Sometimes I find that a track was corrupt, or
had the end cut off or I just plain don't like it! When I get back home I
could download the marks into my PC and either re-rip the track or delete it
or whatever.

Ideally there should be the ability to Mark current/last [0-9] where 0-9
is the mark reason, i.e. 0=corrupt, 1=short, 2=dontlikeit, ...

Paul

Excellent idea. It would be nice if the "tags" that you attach to the track when you mark it are user-assignable in emplode, so when the "tagged track" database is uploaded, you could put your own meanings to the tags.

> It would be nice if the "tags" that you attach to the track when you mark it
> are user-assignable in emplode, so when the "tagged track" database is
> uploaded, you could put your own meanings to the tags.

Well, I don't really care about emplode since I've never used it. But it seems
that if the "mark" function would just add a tag to the *1 fid for the track
such as "mark=3" then the UI could map 3 to whatever you want for you (if
you want it to).

Paul

Unfortunately this wouldn't work like that - we've always planned to add a "mark for deletion on next sync" flag which can be set during playback, but the fids partition is kept read-only the whole time the player is running and so we can't write to the *1 files.

The dynamic data partition (hda3) is designed for this sort of thing, and its contents can be accessed via the protocol - this will be further documented when we've got the dynamic data stuff slightly more concrete (ie: it changed a couple of days ago!)

hugo

> Unfortunately this wouldn't work like that - we've always planned to add a
> "mark for deletion on next sync" flag which can be set during playback, but
> the fids partition is kept read-only the whole time the player is running and
> so we can't write to the *1 files.

Ok, I can see that. But please be a bit more flexible that just "mark for
deletion", after all, I'm not the only driver of our car and my wife wants
to delete half the stuff I like and vice versa :-)

Paul

Ok, I can see that. But please be a bit more flexible that just "mark for
deletion", after all, I'm not the only driver of our car and my wife wants
to delete half the stuff I like and vice versa :-)

I think it is more likely to be "mark for attention" and emplode would be able to show a list of all tunes with the flag set. It wouldn't automatically delete. Mind you, the design is still not settled.

Marking with a reason means complicating the UI. It may not be worth it.

--
Mike Crowe
I may not be speaking on behalf of empeg above :-)

I agree with Mike - it would seem to complicated to put in a "mark for attention". What other reason would you want to mark it for other than deletion? Plus I would hope that you and your wife could get along well enough to not have her delete all the songs.

Paul <xml> wrote:
When playing a track in the car it would be really useful if I could
mark the current and/or the last track. Sometimes I find that a track
was corrupt, or had the end cut off or I just plain don't like it! When
I get back home I could download the marks into my PC and either re-rip
the track or delete it or whatever.

Yes, I would very much like this too. On my home mp3 set-up I
have a preference attached to each track and use that combined with
how-recently-played and keep-with-next information to help steer the
random play. It would be really good to have a way of updating my
preferences on the empeg (even if it didn't actually affect the empeg
play order).

Ultimately, I'd like the same system I have at home on the empeg, but
at least marking bad tracks or tracks I really don't like for playlist
deletion would be a start.

Ideally there should be the ability to Mark current/last [0-9] where
0-9 is the mark reason, i.e. 0=corrupt, 1=short, 2=dontlikeit, ...

I would interpret the numbers differently, but until the marks affect the
empeg play order in some way, that is between me and whatever software
I use to interpret the marks at home. I do like the idea.

Are there plans to use the number keys for something else? It seems
odd that most of the keys on the remote currently don't do anything.

Yes, I would very much like this too. On my home mp3 set-up I
have a preference attached to each track and use that combined with
how-recently-played and keep-with-next information to help steer the
random play. It would be really good to have a way of updating my
preferences on the empeg (even if it didn't actually affect the empeg
play order).

Hm, looks like the kind of behaviour I would like to have on my home setup. What player do you use?

Cheers!

Dragi "Bonzi" Raos
Zagreb, Croatia
#5196

Dragi "Bonzi" Raos wrote:
Hm, looks like the kind of behaviour I would like to have on my home
setup. What player do you use?

It's a collection of shell scripts and a little bit of C to do the random
selection, driving mpg123. I currently update the track preferences
with vi, so it would be nice to have a way to do this by remote control.

--
Robin O'Leary

There's a (presumably simple) program that does something similar. It assigns each track a score. When you play through to the end, the score is incremented by 1. When you skip a track, the score is reduced. When you return to the start of a track after playing it through, the score is increased a bit more. The theory is that it will gradually figure out how much you like the various tracks. You can set your own scores on tracks, of course. I'd like something similar to that on the empeg, I think. The only problem is, it's GPLed, so it can't be included in the "player" without pollution.

Yet another reason why I want custom playmodes. :)

Of course, the concept isn't GPLed, just the code, so this functionality (which is fairly simple) _could_ be built into the player.

Search for pimp3 on freshmeat if you want more info.

Richard.

I think the player already keeps these statistics for you, its just that nothing has been done with them yet.

Term

I just wanted to chime in and say that I think the "flag for deletion on next sync" is a *great* feature and I hope to see it very soon. I was about to post that very suggestion when it occurred to me that someone may already have thought of it.

It's easier for me to rip entire CDs, especially ones I haven't heard, than to pick and choose which track to rip. But right now, I have to keep a mental list of all the tracks I don't like and wnat to get rid of. The "delete flag" would be great. I hope you implement it soon. I do disagree with some others, though, who have said that it should be more complicated than that. It would definitely make the UI way too complex. Just plain old "tag for delete" is fine.

What other reason would you want to mark it for other than deletion?

I would probably end up deleting the files but for the ones that are corrupted, I would like to keep track of them so I can re-encode or download a replacement. Not just delete them, this is why a mark for attention is better than mark for deletion.

Alex Lear

There's a program called mserv (www.mserv.org) which does exactly this. It's designed for offices with communal stereos, but still works very well single-user. It's what I use at home.

Peter

Only mark for deletion ?

How about marking for :
- update of the tag info (i.e. typos or errors)
- moving songs that ended up in the wrong playlist
- songs that have a flaw in them (the odd squeak and crackle) and need to be redone

I know, if it is marked you can always play it again if you don't remember why you marked it in the first place. But for those of us whith chronic memory degradation it would help.

Anyways, good idea, in fact I had come up with it myself today before I found this thread. Maybe something to stuff under *0 ?

Cheers,
Hans



Mk2 - Blue - 080000431